You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version bump 0.0.50 → 0.0.51 for the 7 publishable @threadplane/* libs ahead of cutting the release. Inter-lib peerDeps are "*" so no range updates needed; verify-release-versions --tag v0.0.51 passes (atomic).
Ships the lib work merged since v0.0.50 (structured AgentError, injectThreadRouting, subagent cards, TS DX pass, JSDoc). The tag push after merge triggers npm publish (provenance) + the now-verified SLSA release-provenance flow.
PR Review: chore(release): bump publishable packages to 0.0.51
Gather context
Read CLAUDE.md for repo guidelines (none found)
Review PR diff
Check version consistency across all package.json files
Post findings
This PR is clean. Seven publishable @threadplane/* libs uniformly bumped from 0.0.50 → 0.0.51. All diffs are single-line version changes; no peerDep ranges, exports maps, or publish configs were altered.
Version consistency check: All 7 packages are at 0.0.51 ✓. Non-@threadplane libs (cockpit-*, design-tokens, middleware, etc.) correctly remain on their independent versioning tracks.
Two low-severity observations:
package-lock.json is stale — it still records 0.0.50 for all 7 packages (7 hits). The root lockfile isn't used by npm publish for workspace packages, so this won't block the release, but running npm install after the bump would keep the lockfile in sync and avoid confusion during local dev post-merge.
CHANGELOG.md has no 0.0.50 or 0.0.51 entry — the latest entry is 0.0.47. Since 0.0.50 also wasn't recorded, this appears intentional (changelog tracks milestone releases only, not every patch bump). No action needed unless the team wants to document the shipped features (structured AgentError, injectThreadRouting, subagent cards, TS DX pass, JSDoc) mentioned in the PR description.
No correctness bugs, security issues, type-safety problems, or API regressions found. ✅
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Summary
Version bump 0.0.50 → 0.0.51 for the 7 publishable
@threadplane/*libs ahead of cutting the release. Inter-lib peerDeps are"*"so no range updates needed;verify-release-versions --tag v0.0.51passes (atomic).Ships the lib work merged since v0.0.50 (structured AgentError, injectThreadRouting, subagent cards, TS DX pass, JSDoc). The tag push after merge triggers npm publish (provenance) + the now-verified SLSA release-provenance flow.
🤖 Generated with Claude Code